Moderate: Red Hat OpenShift Distributed Tracing 2.9.0 security update

Related Vulnerabilities: CVE-2023-24534   CVE-2023-24536   CVE-2023-24537   CVE-2023-24538  

Synopsis

Moderate: Red Hat OpenShift Distributed Tracing 2.9.0 security update

Type/Severity

Security Advisory: Moderate

Topic

Updated Red Hat OpenShift Distributed Tracing 2.9 container images are now available.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Description

The Red Hat OpenShift Distributed Tracing 2.9 container images have been released.

Users of Red Hat OpenShift Distributed Tracing 2.8 container images are advised to upgrade to these updated images, which contain backported patches to correct security issues, fix bugs, and include further enhancements.

You can find images updated by this advisory in Red Hat Container Catalog (see References).

Security Fix(es):

  • golang: net/http, net/textproto: denial of service from excessive memory allocation (CVE-2023-24534)
  • golang: net/http, net/textproto, mime/multipart: denial of service from excessive resource consumption (CVE-2023-24536)
  • golang: go/parser: Infinite loop in parsing (CVE-2023-24537)
  • golang: html/template: backticks not treated as string delimiters (CVE-2023-24538)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Solution

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs.

Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:

up2date

This will start an interactive process that will result in the appropriate RPMs being upgraded on your system.

Affected Products

  • Red Hat OpenShift distributed tracing 2 x86_64
  • Red Hat OpenShift distributed tracing for Power, little endian 2 ppc64le
  • Red Hat OpenShift distributed tracing for IBM Z and LinuxONE 2 s390x

Fixes

  • BZ - 2184481 - CVE-2023-24538 golang: html/template: backticks not treated as string delimiters
  • BZ - 2184482 - CVE-2023-24536 golang: net/http, net/textproto, mime/multipart: denial of service from excessive resource consumption
  • BZ - 2184483 - CVE-2023-24534 golang: net/http, net/textproto: denial of service from excessive memory allocation
  • BZ - 2184484 - CVE-2023-24537 golang: go/parser: Infinite loop in parsing
  • TRACING-2968 - Wrong port is exposed for jaeger-production-query resulting in connection refused
  • TRACING-3091 - Tempo operator with TLS does not work on OpenShift
  • TRACING-3142 - Fix ServiceMonitor for gateway
  • TRACING-3143 - tempostack_status_condition metric doesn't get updated in some cases
  • TRACING-3147 - Improve tempo version detection
  • TRACING-3173 - jaeger-operator pod restarting with OOMKilled with the default memory value
  • TRACING-3190 - opentelemetry-operator-controller-manager crashlooping after receiving opentelemetry-operator.v0.74.0-5
  • TRACING-3204 - Remove resource limits for Tempo Operator but keep the resource.requests
  • TRACING-3213 - Validation webhooks panics for invalid tenant configuration
  • TRACING-3243 - OpenTelemetry Collector version is not reported properly after a upgrading
  • TRACING-3312 - When deploying Service Mesh on SNO in a disconnected environment , the Jaeger Pod frequently goes into Pending state
  • TRACING-3322 - 16685 is not properly exposed in the Jaeger Operator
  • TRACING-3396 - Operator monitoring only works when operator is installed in openshift-operators-redhat